Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0972

reference: 461-tree-1
name: 0972
tree-preservation-order: undefined
461-tpo-1
uprn
address-text
point: POINT (-1.028163 50.883034)
geometry: MULTIPOLYGON (((-1.028092 50.883026,-1.028095 50.883040,-1.028105 50.883053,-1.028120 50.883063,-1.028140 50.883069,-1.028162 50.883072,-1.028184 50.883070,-1.028204 50.883064,-1.028220 50.883054,-1.028230 50.883041,-1.028234 50.883027,-1.028231 50.883014,-1.028221 50.883001,-1.028206 50.882991,-1.028186 50.882984,-1.028164 50.882982,-1.028142 50.882984,-1.028122 50.882990,-1.028106 50.883000,-1.028096 50.883012,-1.028092 50.883026)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL